Pipe: Utilize parallelStream for concurrent execution of create, start, stop, and drop pipe tasks to enhance performance#11892
Merged
SteveYurongSu merged 1 commit intoapache:masterfrom Jan 14, 2024
Conversation
SzyWilliam
pushed a commit
to SzyWilliam/iotdb
that referenced
this pull request
Nov 26, 2024
…t, stop, and drop pipe tasks to enhance performance (apache#11892) Currently, when creating a pipe, if there is historical data in the cluster, the pipe will be automatically started. This involves **serially** extracting historical data in each data region. When dealing with large data, timeouts may occur, leading to pipe creation failure. To address this, we are considering parallelizing the above operations using `parallelStream` (inspired by @SteveYurongSu).
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Currently, when creating a pipe, if there is historical data in the cluster, the pipe will be automatically started. This involves serially extracting historical data in each data region. When dealing with large data, timeouts may occur, leading to pipe creation failure. To address this, we are considering parallelizing the above operations using
parallelStream(inspired by @SteveYurongSu).This PR has:
for an unfamiliar reader.
for code coverage.
Key changed/added classes (or packages if there are too many classes) in this PR